fix: get back health check for postgres legacy #3010
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
You can find the image built from this PR at Built from 32f2afb |
Ivansete-status
requested review from
SionoiS,
gabrielmer,
NagyZoltanPeter and
darshankabariya
SionoiS
approved these changes
Sep 4, 2024
waku/waku_archive_legacy/driver/postgres_driver/postgres_healthcheck.nim
Outdated
Show resolved
Hide resolved
waku/waku_archive_legacy/driver/postgres_driver/postgres_healthcheck.nim
Show resolved
Hide resolved
gabrielmer
approved these changes
Sep 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Recovering the health check async task for the legacy driver.
This is needed to be kept because the inserts to the database are made through the legacy store Postgres driver.
What happened is that, if the database was restarted, then the legacy Postgres driver didn't reset the connections pool and therefore, the upcoming inserts failed.
Issue
chore: store node loses connection if database restartscloses #2989